Thank you for your contribution! 🙏 We will review your PR as soon as possible.

🏖️ Over the summer, the response time will be longer than usual due to maintainers taking time off so please bear with us.

While you are waiting, make sure to:

• Add an entry in our changelog in alphabetical order and link related issue
• Update the documentation, if needed
• Add unit & e2e tests for your changes
• GitHub checks are passing
• Is the DCO check failing? Here is how you can fix DCO issues

Learn more about:

• Our contribution guide

Just want to share something when writing e2e tests. When I try to run my new e2e tests locally, the setup command ("go test -v -tags e2e ./utils/setup_test.go") deployed the official KEDA image, which is not convenient for debugging new tests with a changed KEDA. I suggest adding a parameter in the setup command for deploying the custom image repository so that developers can use their KEDA repository for debugging.

Just want to share something when writing e2e tests. When I try to run my new e2e tests locally, the setup command ("go test -v -tags e2e ./utils/setup_test.go") deployed the official KEDA image, which is not convenient for debugging new tests with a changed KEDA. I suggest adding a parameter in the setup command for deploying the custom image repository so that developers can use their KEDA repository for debugging.

It's already supported but not properly documented I think. As KEDA is deployed using make, and Makefile uses variables, you can set those envs (globally o for the command) and that's all.
Let me update the PR with that info

@SpiritZhou @zroubalik PTAL

@SpiritZhou @zroubalik PTAL

It looks great now!

/skip-e2e

lol, although I requested a revision of @zroubalik , looks like GH already took into account the previous approval and the automerger did its job. I guess that I had to dismiss the approval instead or request another review :/